約 6,988,258 件
https://w.atwiki.jp/marketresearch/pages/32.html
Florida Augmented and Virtual Reality Market Scope The Florida Augmented and Virtual Reality-market size was assessed at USD in 2023. Developing number of organizations tapping the nearness Florida Augmented and Virtual Reality market, alongside expanding interests in the Florida Augmented and Virtual Reality Market innovation, is supposed to move the business development. expected to register an exponential CAGR valued at in 2032, is the very large growth connectivity across the globe in today’s modern society The presentation of Florida Augmented and Virtual Reality Market has upset the adopters tasks by driving another degree of client commitment through personalization. The development possibilities can be ascribed to the flooding distinction of area based promoting in the retail Florida Augmented and Virtual Reality business. Joining the advantages of actual shopping experience with advanced environment has become significant for physical retailers. In addition, interests in nearness arrangements are seeing a vertical swing, consequently diminishing their showcasing and promoting costs. Sample Copy of This Report https //www.quincemarketinsights.com/request-sample-71350?utm_source=offpage/pranali Florida Augmented and Virtual Reality Market Competitive Landscape The key players operating the global Florida Augmented and Virtual Reality market, which are playing a major role in market development have been studied extensively in this report are Players Apple Inc., EON Reality , FACEBOOK, Alphabet (Google Inc.), Intel Corporation, MAGIC LEAP, INC. , Marxent Labs, Microsoft Corporation ,Sony Corporation ,zSpace, Inc.. Company overview Florida Augmented and Virtual Reality Market Segmentation The Florida Augmented and Virtual Reality Marker report provides a detailed analysis of the various market segments and their market sizes and CAGRs, to help determine the attractiveness of different segments. It includes market forecasts for different regions, major developments, revenues, etc. the Florida Augmented and Virtual Reality Market is segmented into by type, application, By Component By end-user, and region. In 2023, the Florida Augmented and Virtual Reality technologies ruled the market. Segmentation by Application (Consumer and Enterprise), Organization Size (SMEs and Large Enterprises), and Industry Vertical (Gaming, Entertainment Media, Aerospace Defense, Healthcare, Education, Manufacturing, Retail, and Others) Florida Augmented and Virtual Reality Market Regional Insights The North America region dominated the market with a share in 2021. The North America region is expected to witness significant growth at a CAGR of through the forecast period. Due to the continued implementation of the Florida Augmented and Virtual Reality technologies in the Different sectors, North America led the global market environment, giving out reductions and ramping up alternate promotions are becoming standards. shops may also now give custom designed offers and coupons companies like. in place of sending out classified ads and coupons, the clients about the product info. North American market has been segmented into the US, Canada, and Mexico. justifying support for digital transformation research and development, Infrastructure and manufacturing and widespread government-agency adoption of Florida Augmented and Virtual Reality and Florida Augmented and Virtual Reality applications. North America (United States, Canada and Mexico) Asia-Pacific (China, Japan, Korea, India, Southeast Asia and Australia) South America (Brazil, Argentina) Europe (Germany, France, United Kingdom, Russia and Italy) Middle East Africa (UAE, Egypt, Saudi Arabia, and South Africa) Make an Enquiry for purchasing this Report @ https //www.quincemarketinsights.com/enquiry-before-buying/enquiry-before-buying-71350?utm_source=offpage/pranali Years considered for this report Historical year – 2019-2020 Base year – 2021 Estimated Year -2022 Forecast period – 2023 to 2032 Florida Augmented and Virtual Reality Market Dynamics One of the primary elements driving the development of the worldwide Florida Augmented and Virtual Reality market is the rising consciousness of innovation Increasing Awareness of Florida Augmented and Virtual Reality Technology, Growing Integration into Various Industries, Increase use of Florida Augmented and Virtual Reality. Objectives of this report •To estimate Florida Augmented and Virtual Reality market size on regional and global basis. •To identify major segments in the Florida Augmented and Virtual Reality market and evaluate their market shares and demand. •To provide a competitive scenario for the Florida Augmented and Virtual Reality market with major developments observed by key companies in the historic years. •To evaluate key factors governing the dynamics of the Florida Augmented and Virtual Reality market with their potential gravity during the forecast period. Reasons to Buy This Report •Provides niche Florida Augmented and Virtual Reality market insights for decision about every possible segment helping in strategic decision-making process. •Florida Augmented and Virtual Reality Market size estimation of the market on a regional and global basis. •A unique research design for Florida Augmented and Virtual Reality market size estimation and forecast. •Identification of major companies operating in the Florida Augmented and Virtual Reality market with related developments •Exhaustive scope to cover all the possible segments helping every stakeholder Trending Report Of QMI Mobile Cloud Market https //www.digitaljournal.com/pr/mobile-cloud-market-2023-expected-to-witness-the-highest-revenue-growth-over-forecast-period-from-2032 Telecom Cloud Billing Market https //www.digitaljournal.com/pr/telecom-cloud-billing-market-size-industry-growth-rate-global-share-upcoming-trends-leading-players-products-and-services-overview-forecast-to-2032 5G IoT Market https //vk.com/@750505376-5g-iot-market-2023-sales-revenue-top-manufacturers-share-gro About Us QMI has the most comprehensive collection of market research products and services available on the web. We deliver reports from virtually all major publications and refresh our list regularly to provide you with immediate online access to the world’s most extensive and up-to-date archive of professional insights into global markets, companies, goods, and patterns. Contact us Quince Market Insights Phone +1 208 405 2835 Email sales@quincemarketinsights.com Website https //www.quincemarketinsights.com/
https://w.atwiki.jp/220yearsafterlove/pages/65.html
http //20yearsafterlove.blog111.fc2.com/
https://w.atwiki.jp/220yearsafterlove/pages/64.html
http //20yearsafterlove.blog111.fc2.com/
https://w.atwiki.jp/220yearsafterlove/pages/63.html
http //20yearsafterlove.blog111.fc2.com/
https://w.atwiki.jp/wixwiki/pages/41.html
「SimpleInstaller」の中でComponentというタグが出現した。このComponentというタグだが、私個人としてはWiXを理解する上で非常に重要なキーワードの一つだと考えている。 というのは、インストーラが行う様々なアクションの大半がComponentタグに含まれている(Componentタグの直接の子要素になる)ためだ。つまり、Componentタグに含まれるタグ = インストーラが実行できる大半のアクション ということだ。マニュアルでComponentタグの子要素をじっくり眺めることで、WindowsInstallerでどんなことができるのか理解できる。 余談だが、私がこの事実に気づいたのはこの記事を書き始めるわずか数日前だ。WiXに出会ってから数ヶ月間、WiX(WindowsInstaller)で何ができるのかいまいちわからず、どこを調べればよいのかもわからなかったため、結局インストーラを補助する外部プログラムを作りこむという、今考えると馬鹿馬鹿しいことを延々やってきた。これを読んだ方々は私と同じ道を歩まないよう、マニュアルでComponentタグの子要素に少なくとも一度はざっと目を通すことをお勧めする。(英語が苦手な私ですら、タグ名を見ればなんとなくわかるレベルのものなので気楽に眺めてみてほしい) (結論の無い話その1)Component内の実行タイミング Componentタグに関連する内容に少し触れておこう。 ドキュメントを見てわかる通り、Componentタグの子要素は実に様々なものがある。そしてこれらの要素は、記述方法が全く統一されていない点に注意しなくてはならない。 特に戸惑うのは「いつ実行されるのか」という点だ。例えば「SimpleInstaller」の例を見てみよう。 Component Id="COMPONENT1" ...省略... File Id="MAINFILE" Name="TEST.TXT" / /Component Componentタグの中にFileタグがあるが、いつ配置するとも削除するとも書いていない。にもかかわらず、インストールするとこのファイルが配置され、アンインストールするとこのファイルが削除される。 別の例を見てみよう。 Component Id="COMPONENT1" ...省略... RemoveFile Id="REMOVEFILE" Name="TEST.TXT" On="install" / /Component これはインストール時にTEST.TXTというファイルを消すコードだ。RemoveFileというタグの中にOnという属性があることがわかるだろう。RemoveFileタグにおけるOn属性が取りうる値は、「install」と「uninstall」、そして「both」がある。つまり、このOn属性の値によって、インストール時に削除するのか、アンインストール時に削除するのか、それともどちらのときも削除するのかをコントロールすることになる。 このようにComponentの子要素は、実行タイミングの記述の仕方をはじめとして、色々と異なる部分が多い。マニュアルを見てもタグによっては明確に書かれていないことが多い。ここまで読んできた皆さんはガックリするかもしれないが、結論としてはサンプルコードを作って試行錯誤する以外に、確実に仕様を知る方法はなさそうだ、ということだ。 (結論の無い話その2)Componentの矛盾 インストーラはComponentの単位でインストールやアンインストールを行う。また、インストールやアンインストールをするかどうか、という判断もComponent単位で行う。 例えばある種のインストーラ(典型的な例で言えば、MicrosoftのOfficeやVisualStudio等のインストーラ)では、インストールする機能を選択できることをご存知だろう。このインストールする機能を選択するというのは、内部的にはComponentタグごとにインストールするかどうかを判断することで実現している。 それでは、たくさんのファイルを常に全てインストールする、という場合であればComponentタグ1つの中に全てを押し込めばよいのだろう、と思うかもしれない。ところが、実際にはそんなに簡単にはいかない。例えば、複数のディレクトリにファイルをインストールしたいときなどはその典型例だ。 Directory Id="TARGETDIR" Name="SOURCE" Directory Id="DIR1" Name="DIR1" Component Id="COMP1" ...省略... / File Id="FILE1" Name="TEST1.TXT" / /Component /Directory Directory Id="DIR2" Name="DIR2" Component Id="COMP2" ...省略... / File Id="FILE2" Name="TEST2.TXT" / /Component /Directory /Directory 上記の例は、C \DIR1\TEST1.TXT というファイルと C \DIR2\TEST2.TXT という二つのファイルをインストールしようとした場合の書き方だが、見て判るとおりComponentが2つになってしまう。これを1つにすることは(恐らく・・)できない。というのもWindowsInstallerではDirectoryをComponentの中に含めることができないため、このような書き方にならざるを得ないのだ。 このような「なんか変だ・・・?」という構造がWindowsInstaller(あるいはWiX)にはいくつもある。なぜそうなのかは知らなくて問題ない。しかし残念ながらWindowsInstallerの仕様である以上、それに従わずにはインストーラは作れない。 visitor - (today - ) Author nagatyo コメント (注:コメントは管理人が適宜消去する場合があります) 名前 コメント すべてのコメントを見る
https://w.atwiki.jp/elvis/pages/902.html
7 Habits Of Highly Effective People 15th Anniversary Edition Stephen R. Covey I Know the Alphabet Pre-School (Step Ahead Plus Workbook) Golden Books?Stephen R. Covey Seven Habits of Highly Effective People, Miniature Edition Stephen R. Covey 7 Habits of Highly Effective People (3CD) Stephen R. Covey I'm Ready for School (Golden Step Ahead) Golden Books?Stephen R. Covey The 7 Habits of Highly Effective People Personal Stephen R. Covey First Things First To Live, to Love, to Learn, to Leave a Legacy Stephen R. CoveyA. Roger Merrill?Rebecca R. Merrill? Cursive Writing Grades 2-3 (Golden Step Ahead Plus) Golden Books?Stephen R. Covey The 7 Habits Of Highly Effective People Stephen R. Covey Daily Reflections for Highly Effective People Living the Seven Habits Stephen R. Covey The Ugly Duckling Goes To Work Wisdom For The Workplace From The Classic Tales Of Hans Christian Andersen Stephen R. CoveyMette Norgaard?Hans Christian Andersen Principle-Centered Leadership Stephen R. Covey The 8th Habit From Effectiveness to Greatness Stephen R. Covey 7 Habits of Highly Effective People Stephen R. Covey Principle-Centered Leadership Stephen R. Covey The 8th Habit Personal Workbook Stephen R. Covey The 7 Habits of Highly Effective Teens Workbook (The 7 Habits) Stephen R. Covey The 8th Habit From Effectiveness to Greatness Stephen R. Covey The Power of the 7 Habits Applications and Insights Stephen R. CoveyStephen R. Covet? Los 7 Habitos de la Gente Altamente Efectiva La Revolucion Etica en la Vida Cotidiana y en la Empresa Stephen R. Covey Math Skillbuilders Grades 3-4 (Golden Step Ahead Plus) Golden Books?Stephen R. Covey The 7 Habits of Highly Effective Families Building a Beautiful Family Culture in a Turbulent World Stephen R. Covey The 7 Habits of Highly Effective People Powerful Lessons in Personal Change Stephen R. Covey The 7 Habits of Highly Effective People Stephen R. Covey Principle Centred Leadership Stephen R. Covey First Things First Every Day Because Where You're Headed Is More Important Than How Fast You're Going Stephen R. CoveyA. Roger Merrill?Rebecca R. Merrill? The 7 Habits of Highly Effective People (Large Card Decks) Stephen R. Covey The 8th Habit From Effectiveness to Greatness Stephen R. Covey The Speed of Trust The One Thing that Changes Everything Stephen M. R. Covey?Rebecca R. Merrill? The 7 Habits Family Collection Leadership Where It Matters Most (Your Coach in a Box) Stephen R. Covey Living The 7 Habits Inspiring Stories, Applications and Insights (Your Coach in a Box) Stephen R. Covey The 7 Habits of Highly Effective People (Covey) Stephen R. Covey Before I Do Math Preschool (Golden Step Ahead) Stephen R. Covey Los 7 Habitos De Las Familias Altamente Efectivas Stephen R. Covey Six Transcendent Events Using the Lord's Model to Solve Life's Problems Stephen R. Covey Prisoners Of Our Thoughts Viktor Frankl's Principles At Work Alex Pattakos?Stephen R. Covey Viviendo Los 7 Habitos Historias Que Engrandecen Stephen R. Covey 7 Habits of Highly Effective People Stephen R. Covey Living the Seven Habits Stephen R. Covey The 7 Habits of Highly Effective Families (Books of the) Stephen R. Covey Principle-Centered Leadership Stephen R. Covey Living the 7 Habits Applications and Insights Stephen R. Covey Stephen R. Covey Live from the U.K How to Create Unstoppable People, Teams and Organizations Stephen R. Covey Loving Reminders for Couples 60 Affectionate Notes Stickers for Those Close to Your Heart (Loving Reminders) Stephen R. Covey How to Develop a Family Mission Statement (The 7 Habits Family Leadership Series) Stephen R. Covey How to Develop and Use a Personal Mission Statement Stephen R. Covey The 7 Habits of Highly Effective Teens Journal Stephen R. CoveyDebra Harris? The Nature of Leadership Stephen R. Covey Choice Choosing the Proactive Life You Want to Live (The Portable 7 Habits Series) Stephen R. Covey The Power Principle Influence With Honor Stephen R. CoveyBlaine Lee? Mission Possible Stephen R. CoveyAlison Brown?Deepak Chopra?Stephen E. Roulac?John F. Demartini?Les Brown?Celeste B. Longacre?Patricia Ball?Pat Summitt?Rosemarie, Ph.D. Rossetti? Mission Possible Stephen R. CoveyJohn Gray?Nando Parrado?Joe Calloway? 7 Habits of Highly Effective People Stephen R. Covey Living the 7 Habits Stories of Courage and Inspiration Stephen R. Covey Building Family Relationships Stephen R. Covey Renewal Nourishing Mind, Body, Heart, and Soul (The Portable 7 Habits Series) Stephen R. Covey Vision Defining Your Destiny in Life Stephen R. Covey Purpose Focusing on What Matters Most Stephen R. Covey Trust Sharing Ideas, Insights, and Understanding (The Portable 7 Habits) Stephen R. CoveyTammy Smith? 7 Habits of Highly Effective People Stephen R. Covey Der 8. Weg. Hoerbuch . Mit Effektivitaet zu wahrer Groesse Stephen R. Covey The 7 Habits of Highly Effective Families Stephen R. Covey Stephen R. Covey Mixed The 7 Habits of Highly Effective People, Living the 7 Habits, First Things First, Principle Centered Leadership, the 7 Stephen R. Covey The 7 Habits Family Collection Building a Beautiful Family Culture in a Turbulent World Stephen R. Covey The 7 Habits Journal Stephen R. Covey The 7 Habits Family Journal Stephen R. Covey Balancing Work Family (Family Leadership Collection) Stephen R. Covey Liderazgo Centrado En Principios Stephen R. Covey Sharpen the Saw (7 Habits Signature Series) Stephen R. Covey The 8th Habit From EffectivenessTo Greatness Stephen R. Covey The 8th Habit From Effectiveness To Greatness Stephen R. Covey Habit 4 Think Win-win The Habit of Mutual Benefit (The 7 Habits of Highly Effective People) Stephen R. Covey Habit 6 Synergize (The 7 Habits Signature Series) Stephen R. Covey Spiritual Roots of Human Relations Stephen R. Covey The 7 Habits Signature Series Stephen R. Covey The 7 Habits of Highly Effective Families Stephen R. Covey Die effektive Fuehrungspersoenlichkeit. Management by principles Stephen R. Covey Die 7 Wege zur Effektivitaet. Prinzipien fuer persoenlichen und beruflichen Erfolg Stephen R. Covey Der Weg zum Wesentlichen. Zeitmanagement der vierten Generation Stephen R. CoveyA. Roger Merrill?Rebecca R. Merrill? Meditaciones Diarias Para LA Gente Altamente Efectiva Stephen R. Covey Spiritual Roots and Human Relation Stephen R. Covey How to Succeed With People Stephen R. Covey Spiritual Roots of Human Relations Stephen R. Covey The Seven Habits of Highly Effective Families Building a Beautiful Family Culture in a Turbulent World Stephen R. Covey The Divine Center Stephen R. Covey Marriage and Family Gospel Insights Stephen R. CoveyTruman Madsen? In Search of Quality 4 Unique Perspectives, 43 Different Voices Stephen R. CoveyKen Shelton? Los 7 Habitos De Las Familias Altamente Efectivas / The 7 Habits Of Highly Effective Families Construyendo Una Hermosa Cultura Familiar En UN Mundo Turbulento Stephen R. Covey Healing Your Family History 5 Steps to Break Free of Destructive Patterns Stephen R. CoveyRebecca Linder Hintze? Principle Centered Leadership Stephen R. Covey Principle-centered Leadership Stephen R. Covey Living the 7 Habits Stephen R. Covey Living the 7 Habits Stories of Courage and Inspiration Stephen R. Covey Los 7 Habitos De LA Gente Altamente Efectiva (Paidos Plural, 1) Stephen R. Covey Shapes Colors Preschool Activity Cards (Golden Step Ahead) Golden Books?Stephen R. Covey The Power of the 7 Habits Applications and Insights Stephen R. Covey First Things First Stephen R. CoveyA. Roger Merrill?Rebecca R. Merrill? The Seven Habits of Highly Effective People Restoring the Character Ethic Stephen R. Covey Living the Seven Habits Stephen R. Covey Quest Discovering Your Human Potential (Quest (Simon Schuster)) Stephen R. CoveyThomas Moore?Bernie S. Siegel?David Whyte?Marianne Williamson?Deepak Chopra? Quest The Spiritual Path to Success (Quest , Vol 2) Mark Victor Hansen?Thomas Moore?Gabrielle Roth?Bernie S. Siegel?David Whyte?Marianne Williamson?Stephen R. Covey Los 7 Habitos De Las Personbas Altamente Eficaces Stephen R. Covey The 7 Habits of Highly Effective People Restoring the Character Ethic (A Fireside Book) Stephen R. Covey Principle-centered Leadership Stephen R. Covey Daily Reflections for Highly Effective People Stephen R. Covey Principle Centered Leadership Stephen R. Covey Principle-Centered Leadership/Audio Cassette Stephen R. Covey Primero, Lo Primero/ First Things First Everyday Reflexiones Diarias Stephen R. Covey First Things First Stephen R. CoveyA.Roger Merrill? First Things First To Live, to Love, to Learn, to Leave a Legacy Stephen R. CoveyA. Roger Merrill?Rebecca R. Merrill? First Things First Stephen R. Covey 7 Habits Journal and 7 Habits People Stephen R. Covey Seven Habits of Highly Effective Families Sandra Merrill Covey?Stephen R. Covey Reflections for Highly Effective People Stephen R. Covey The 7 Habits of Highly Effective Familes Stephen R. Covey LA Caja / The Box Arbinger Institute?Stephen R. Covey Synergy Connecting to the Power of Cooperation (The Portable 7 Habits) Stephen R. CoveyTammy Smith? The Four Disciplines Of Execution Stephen R. CoveyJennifer Colosimo? The 8th Habit Stephen R. Covey Living the 7 Habits The Courage to Change Stephen R. Covey 7 Habits of Highly Effective People Stephen R. Covey First Things First Stephen R. CoveyA.Roger Merrill? Principle-centered Leadership Stephen R. Covey Living the Seven Habits Stephen R. Covey The 7 Habits of Highly Effective Families Stephen R. Covey Managing Change in Crisis Stephen R. Covey 7 Habits Journal Stephen R. Covey The 7 Habits Journal Stephen R. Covey Lead Or Get Off The Pot! The Seven Secrets Of A Self-made Leader Stephen R. CoveyPat Croce?Bill Lyon? El Liderazgo Centrado En Principios Stephen R. Covey The Speed of Trust Stephen M.R. Covey? The 7 Habits of Highly Effective Teens Stephen R. Covey Meditaciones Diarias Para La Gente Altamente Efect Stephen R. Covey The 8th Habit From Effectiveness to Greatness [DVD Region Free] http //logbord.lolipop.jp/asin/Books/0743274180/? Stephen R. Covey Der 8. Weg. Von der Effektivitaet zur wahren Groesse Stephen R. Covey 8th Habit Personal Workbook Stephen R. Covey First Things First Stephen R. Covey El 8 Habito De la Effectividad a la Grandeza / From Effectiveness to Greatness (Empresa / Business) Stephen R. Covey The Power of the 7 Habits Stephen R. Covey 7 Habits of Highly Effective People Stephen R. Covey Living the 7 Habits Stephen R. Covey First Things First Stephen R. Covey Principle Centered Leadership Stephen R. Covey The 8th Habit Stephen R. Covey Beyond the 7 Habits Stephen R. Covey Living the 7 Habits Stephen R. Covey The 7 Habits of Highly Effective People Stephen R. Covey Focus Achieving Your Highest Priorities Stephen R. Covey Primero, Lo Primero Stephen R. Covey The Power of the 7 Habits Stephen R. Covey First Things First Every Day Because Where You're Headed Is More Important Than How Fast You're Going Stephen R. CoveyA. Roger Merrill?Rebecca R. Merrill? Meet the Experts Leadership (Meet the Experts) Dale CarnegieStephen R. CoveyLaurie Beth Jones Los Habitos De Las Personas Altamente Eficaces Stephen R. Covey Meet the Experts Business Skills (Meet the Experts) David Allen?Robert M. Bramson?Stephen R. Covey The Seven Habits of Highly Effective People Restoring the Character Ethic (G K Hall Large Print Reference Collection) Stephen R. Covey The 8th Habit From Effectiveness to Greatness (Running Press Miniature Editions (Hardcover)) Stephen R. Covey Los Siete Habitos de La Gente Altamente Efectiva Stephen R. Covey Stephen Covey - Live in London Stephen R. Covey El Liderazgo Centrado En Principios Stephen R. Covey Servant Leadership A Journey into the Nature of Legitimate Power and Greatness Stephen R. CoveyRobert K. Greenleaf?Larry C. Spears? Focus Achieving Your Highest Priorities Self-Directed Audio Workshop Stephen R. CoveyHyrum Smith?Steve Jones? Los 7 Habitos De Las Familias Altamente Efectivas Construyendo Una Hermosa Cultura Familiar En UN Mundo Turbulento Stephen R. Covey Meditaciones Diarias Para La Gente Altamente Efectiva Stephen R. Covey Primero Lo Primero Stephen R. CoveyA. Roger Merrill?Rebecca R. Merrill? Division Flash Cards (Pack of 12) Stephen R. Covey First Things First Stephen R. CoveyA. Roger Merrill?Rebecca R. Merrill? The 7 Habits of Highly Effective People Powerful Lessons in Personal Change Stephen R. Covey Living the Seven Habits Stories of Courage and Inspiration Stephen R. Covey Habit 5 Seek First to Understand Then to Be Understood The Habit of Mutual Understanding (The 7 Habits) Stephen R. Covey Die 7 Wege zur Effektivitaet. 10 CD's . Prinzipien fuer persoenlichen und beruflichen Erfolg Stephen R. Covey The 7 Habits of Highly Effective Families Stephen R. Covey El Liderazgo Centrado En Principios Stephen R. Covey El 8o Habito de La Efectividad a la Grandeza (Paidos Empresa) Stephen R. Covey Business Think Stephen R. Covey Mission Possible Learn How to Reach Your Potential from Some of the World's Most Successful Possibility Thinkers Stephen R. CoveyBrian Tracy? Grandeza Para Cada Dia/ Everyday Greatness Dr. Stephen R. Covey?David K. Hatch? Beyond the 7 Habits Stephen R. Covey The 7 Habits of Highly Effective People Stephen R. Covey Habit 1 Be Proactive (The 7 Habits) Stephen R. Covey The 8th Habit From Effectiveness to Greatness Stephen R. Covey Stephen Covey Masterclass Stephen R. Covey Habit 2 Begin With the End in Mind (7 Habits of Highly Effective People) Stephen R. Covey Habit 3 Put First Things First (7 Habits of Highly Effective People Signature Series) Stephen R. Covey Principle-Centered Leadership Stephen R. Covey Live in London Stephen R. Covey Habit 7 Sharpen the Saw The Habit of Renewal Stephen R. Covey Primero, Lo Primero / First Things First (Paidos Plural) Stephen R. Covey First Things First Stephen R. Covey Loving Reminders for Kids 60 Nurturing Notes and 60 Stickers (Loving Reminders) Stephen R. CoveyFranklin Covey Company?Franklin Covey Company? 1st Things 1st Stephen R. Covey Los 7 Habitos De La Gente (CD) Stephen R. CoveyRandom House Mondadori Los 7 Habitos De Las Personas (CD) Stephen R. CoveyRandom House Mondadori Primero, Lo Primero Stephen R. Covey Principle-Centered Leadership Stephen R. Covey I Sette Pilastri Del Successo Stephen R. Covey Los 7 Habitos de La Gente Eficaz Stephen R. Covey Los 7 Habitos De La Gente Altamente Efectiva Stephen R. Covey Covey Audio Learning Library Stephen R. Covey Principle-Centered Leadership (Your Coach in a Box) Stephen R. Covey Los 7 Habitos De Las Personas Altamente Efectiva Poderosas Lecciones Para El Cambio Personal Stephen R. Covey Los 7 Habitos De Las Familias Altamente Efectivas Creando Una Floreciente Cultura Familiar En UN Mundo Turbulento Stephen R. Covey Primero Lo Primero Stephen R. Covey Die sieben Wege zur Effektivitaet. 4 Cassetten Stephen R. CoveyMarc-Roman Trautmann?Holger Lappe? Quest Stephen R. CoveyThomas Moore?Bernie S. Siegel?Marianne Williamson? Die sieben Wege zur Effektivitaet Stephen R. Covey Der Weg zum Wesentlichen. Jubilaeumsausgabe. Zeitmanagement der vierten Generation Stephen R. CoveyA. Roger Merrill?Rebecca R. Merrill? So leben Sie 'Die sieben Wege zur Effektivitaet'. Das bewaehrte Covey-Erfolgskonzept in der Praxis Stephen R. Covey First Things First Stephen R. CoveyA.Roger Merrill? Der Weg zum Wesentlichen. Zeitmanagement der vierten Generation Stephen R. CoveyA. Roger Merrill?Rebecca R. Merrill? Die sieben Wege zur Effektivitaet. 2 CDs. Stephen R. Covey Der Weg zum Wesentlichen. 2 CDs. . Zeitmanagement der vierten Generation Stephen R. CoveyA. Roger Merrill?Rebecca R. Merrill? The 7 Habits of Highly Effective People 15th Anniversity Edition Stephen R. Covey 7 Habits of Highly Effective Families Stephen R. Covey The 7 Habits of Highly Effective People Stephen R. Covey The Four Disciplines of Execution Stephen R. CoveyJennifer Colosimo? Quest Stephen R. Covey The 7 Habits of Highly Effective People Stephen R. Covey The 7 Habits of Highly Effective People Stephen R. Covey The 7 Habits Signature Series Set Stephen R. Covey The 8th Habit Stephen R. Covey The 8th Habit Stephen R. Covey Beyond the 7 Habits Stephen R. Covey The Power Principle Stephen R. CoveyBlaine Lee? First Things First Stephen R. Covey A Passion for Life Breakthrough Views on Conscious Living, Aging, Dying, and Renewing Our Passions in Life (Quest Passion for Life Series, V. 1) All-Star Roster?Iyanla Vanzant?Stephen R. CoveyRichard Carlson?Deepak Chopra?Bernie S. Siegel? Focus Achieving Your Highest Priorities Stephen R. Covey First Things First Every Day Because Where You're Headed Is More Important Than How Fast You're Going Stephen R. CoveyA. Roger Merrill?Rebecca R. Merrill? Los Siete Habitos De LA Gente Altamente Efective Stephen R. Covey Habit 1 Be Proactive The Habit of Choice Stephen R. Covey The Speed of Trust The One Thing That Changes Everything Stephen M. R. Covey? 7 Habits of Highly Effective People Restoring the Character Ethic Stephen R. Covey Habit 2 Begin With the End in Mind The Habit of Vision Stephen R. Covey Cal 99 7 Habits of Highly Effective People Calendar Stephen R. Covey The 7 Habits of Highly Effective People 2007 Calendar 17 Month 2007 Magnetic Wall Calendar Stephen R. Covey Quest Stephen R. Covey Daily Reflections for Highly Effective People Stephen R. Covey Habit 3 Put First Things First The Habit of Integrity And Execution Stephen R. Covey Living the 7 Habits Stories of Courage and Inspiration Stephen R. Covey Living the Seven Habits Stories of Courage and Inspiration Stephen R. Covey Living The 7 Habits Stephen R. Covey Principle-centered Leadership Stephen R. Covey Les 7 Habitudes Des Gens Efficaces Stephen R. Covey Leadership Stephen R. Covey Die sieben Wege zur Effektivitaet Stephen R. Covey Die sieben Wege zur Effektivitaet Stephen R. Covey Loving Reminders to Make Kids Laugh Stephen R. Covey Daily Reflections for Highly Effective People Stephen R. Covey Der Weg zum Wesentlichen. Zeitmanagement der vierten Generation Stephen R. CoveyA. Roger Merrill?Rebecca R. Merrill? The 7 Habits of Highly Effective Families (Books of the) Stephen R. Covey Der Weg zum Wesentlichen. 4 Cassetten. Zeitmanagement der vierten Generation Stephen R. CoveyA. Roger Merrill?Rebecca R. Merrill?Holger Lappe?
https://w.atwiki.jp/gyakusai/pages/56.html
On the Wright Track The Writers of Phoenix Wright s Sequel DiscussTheirNew Case http //www.nintendo.com/newsarticle?articleid=5mLTEfSPVUJJqjyIiQb3nJa-vdRURKQh page=currentNews Nintendo Power How would you compare the localization of Phoenix Wright to other gamesyou’veworked on? Nintendo Power: PhoenixWrightの翻訳は、あなたが担当した他のゲームの翻訳と比較してどうですか? Brandon Gay As far as text alone, Phoenix Wright is one of our largest games tolocalize.Since it is a text-based game, there is a high emphasis on flow andconsistencyamong the characters. This is in contrast to other games such asDevil May Cryor Resident Evil where the story almost takes a backseat to theaction of thegame. It isn’t that the story is unimportant in those games, buta player maybe more apt to look past the story in those games since the mainfocus in thosegames is the action. With Phoenix Wright you are trying to conveyan entireworld and in-depth characters through text alone. This makes it achallenge topresent characters that are applicable to the US market. Thesecharacters allstarted off as much more Japanese-style characters, with jokesand dialoguedesigned with the Japanese player in mind. So part of the challengewas to makethe characters and the world itself relevant to an Americanaudience. Also, inworking on Justice for All, we had to make sure thecharacters that reappearfrom the first Phoenix Wright Ace Attorney game stayedconsistent with howthey behaved in that game. The fans of Phoenix Wright havegrown quiteaffectionate to the characters that populate this world, so wewanted to staytrue to the characters they have come to either love or hate.Brandon Gay: テキスト量から、PhoenixWrightは翻訳には大きなゲームのうちのひとつです。テキストベースのゲームなので、キャラクターたちの間に一貫した流れがあります。このことは、物語がゲームの流れから引いた位置にある、DevilMayCryやResidentEvil(バイオハザード)とは対照的です、ですが、DevilMayCryやResidentEvilが物語が重要ではないという意味ではありません。しかし、これらのゲームはアクションに重きを置いているので、プレイヤーはより、物語を低めに見る傾向があるかもしれません。PhoenixWrightはテキストのみで、キャラクターの内面や世界観を伝えることになります。これはアメリカの市場で通じるようなテキストを発売する挑戦となります。原作は日本語と日本的な文章、日本語のジョークや文字表示の方法(ダイアログ)で設計されています。そこで、アメリカ人向けに、アメリカ的なテイストにキャラクターや世界観をもっていくことを試みました。また、JusticeforAll(海外版2)では、初めてPhoenixWrightに触れるプレイヤーに、再登場人物をわかるようにしなければなりませんでした。PhoenixWrightのファンはキャラクターに思い入れがありますので、私たちは味方から嫌な敵キャラまで、忠実に訳したかったのです。 JP Kellams There is a fair amount of pressure because of how well the localizationforPhoenix Wright was received, but there is also quite a bit offreedomcreatively. All titles require you to match the localization to the toneof thegame and Japanese text. In a serious game, an off-the-wall joke wouldbedistracting. However, with Justice for All, the subject and style of thegamegive you the creative ability to add humor and little touches thatjustwouldn’t fit into other games. JP Kellams: PhoenixWrightの翻訳をいかに良くできたかというプレッシャーがありますが、オリジナルの部分もわずかに作る事ができます。このシリーズの翻訳は、日本語版テキストのタイミングと合わせなくてはなりません。 (※訳注 英語版は、日本語版が1画面22文字で構成されていることに合わせて、1画面ごとの翻訳がなされている。SVCまたはSVO、SVOOの構文を日本語文法に合わせることは大変な作業だと、プレイして感じた) シリアスなゲームにおいて、突飛な冗談は気が散ります。しかし、JusticeforAllでは、他のゲームの翻訳とは異なる、創造的な能力、ユーモアが必要です。 Janet Hsu Personally, compared with other titles I have worked on, I feel thatPhoenixWright demands a lot of yourself and your ability to understand thecharacterson a deeper level. Because some of the characters have a lot of depthto them,you almost have to become them in a sense to get the nuance andmotivations intheir lines right.Janet Hsu: 個人的に感じたことは、私が今まで翻訳してきたゲームと比べて、PhoenixWrightではより深くキャラクターを理解する能力が要求されるということです。幾つかのキャラクターは、非常に奥深い性格なので、そのニュアンスと、行動する上での動機付けを正しくするために、ある意味では、そのキャラクター自身にならなくてはなりません。 NP What was your philosophy for determining North American character names? NP: 北米版でのキャラクターの名前を決定するためのコンセプトは何でしたか? Brandon A lot of the character names were determined with the Japanese names inmind.Some of the Japanese names were already quite clever, so we wanted to keepthesame feel they had. Obviously, with some names, they had to be changedquitedrastically from their Japanese counterparts. But we wanted to keep thehumoraspect of the Japanese names when we came up with the English names.Sincethere is so much underlying humor in Phoenix Wright Ace Attorney, wewantedthe names to have the same type of double meanings that the Japanesenameshad. Brandon: ほとんどのキャラクターは日本名から決定しました。日本のキャラ名は非常に面白かったので、私たちもその雰囲気を継承したかったのです。幾つかは日本名とは全く異なるものに変えざるを得なかったのですが、日本語でのユーモアな雰囲気は保ちたかったのです。PhoenixWright AceAttorneyの元になるユーモアから、日本語版のようなダブルミーニングになる名前を付けたいと思いました。 JP There is this mystique that names get handed down from upon high and areforcedupon us. Not so. For my part, I try to make names that lean on popularcultureso they have a tinge of familiarity. For instance, the logic behind thename ofLawrence “Moe” Curls should be instantly indefinable by olderplayers, butshould still give younger players that instant identification thathe is aslapstick-loving clown. This popular-culture identification is somethingthatShu Takumi [the game’s director and creator] does very well with theJapanesenaming and I try to follow that spirit when it comes to naming.JP: 仰々しい名前でミステリアスな雰囲気は必要ない。私の担当部分では、親しみをもてるように、大衆文化からとっていこうと思いました。例えば、Lawrence“Moe”Curls(トミーの本名)の名前のネタは、喜劇役者のピエロであるということを、すぐに識別できるようにしてあります。この方法は日本語版ディレクターの巧氏がとる方法で、私はこの精神にのっとって名前をつけるようにしました。 (※訳注 トミーの英語名はTheThreeStoogesという、1930年代から、第2次世界大戦の戦前戦後を通じて活躍したコメディ・チームのメンバーの名前「Larry,Moe,Curly」を使用している模様) Janet I was not as pop-culture-oriented as JP since in his episode, Takumi-sanhadused more pop culture references in the original Japanese, but for cases 1and2, I kept the play-on-words naming the first Phoenix Wright is so famousfor.However, due to the more dramatic feel of the last case, I kept more tothenaming sense Takumi-san used there and created names that sounded morelikereal names, but had deeper meanings (sometimes more than one) tothem.Incidentally, Takumi-san personally approved all the English names inthisgame. I can now fondly look back and remember we had an interestingtimebouncing names back and forth for a few days for one of the characterswhich hethought didn’t convey the same feeling as the Japanese [name]. Janet: 私はJP程大衆文化を根底にはしませんでした、巧氏は日本語版で大衆文化を引用した名前を付けましたが、私は1話と2話のために、1作目では特徴であるダジャレをよく使いました。しかし、最終話のようなドラマティックな展開のために、リアルでもありそうな名前を使い、そしてそれらには(時には1作目以上の)意味を持たせました。ちなみに、巧氏は、このゲームにおいて、考え出した英語名を全て承認しました。日本名と同じ雰囲気を伝える事ができないと、ある名前に非常に悩み、2、3日かけたことも良い思い出です。 NP If you worked on the first Phoenix Wright, what was the process likedeterminingPhoenix’s name? What other names were considered but rejected?Also, pleaseelaborate on Oldbag’s name. NP: 1作目に取り組むとき、Phoenixの名前はどのように決定しましたか? 他に候補はありましたか? また、Oldbag(オバチャン)のネーミングについて教えてください。 Brandon Ahh, making me go back into the memory banks for this one [laughs]. Weactuallycame up with a rather large list of names for the Phoenix Wrightcharacter. Weconsulted with our American branch on what would be the best namefor the titlecharacter. It was agreed that Phoenix Wright would be the best andmostappropriate name for the title character. As for Wendy Oldbag, I believe that name originated from the mind of AlexSmith,who translated the first title, but the story behind it is amystery. Brandon: (笑い)思い出してみますと、実は、私たちはPhoenixWrightの性格から考えた大きな名前候補リストを作成したのです。そして、主役の名前としてベストなものをカプコンUSAと相談しました。その中でPhoenixWrightが最も良いということで同意し、決定しました。 WendyOldbag(大場カオル)については、翻訳担当のAlexSmith氏が決定したと思います。そのバックグラウンドはわかりませんが。 (※訳注 AlexSmith氏は、ファイナルファンタジー10やグイン・サーガの翻訳を担当している人物。) Eric Bailey We wanted to make sure that [Phoenix’s] first name was something thatwouldreally stand out with players, and so we went back and forth withthetranslator and the R D team to determine the name that would work.Duringthe brainstorming, when everyone was throwing out whatever names came tomind,there was a wide range of them-everything from Cole to Wilton-but in theendPhoenix had a good ring to it and symbolized rising from the ashes, perfectforthe game’s theme, which is turnabouts. We also needed a shortened formofPhoenix for some of the characters to use in the dialog and the finalnicknamearrived at was “Nick” since it sounded natural but was stillreasonablegiven the sound of “Phoenix.” Of course, we always made sure toexplain anyof the naming choices to the game’s creator to make sure it wassomething hewould like and he ended up liking Phoenix Wright as well. Unfortunately no one here seems to recall the exact story behind howWendyOldbag’s name came about, so it will go down as a mystery. In the end,it wasa perfect choice for the character and works well with the dialog aroundher,so we are glad it became her final name. It’s hard to imagine her anyotherway now.Eric Bailey: 主人公の名前は目立つものがいいと私たちは考えていました。そして、翻訳チームと開発チームの間を行ったり来たりして、思いついた名前案がボツになり続けていたのですが、risingfromtheashes(※訳注 英語版5話「蘇る逆転」のサブタイトル、灰から復活するの意)から、Phoenix(灰から復活する不死鳥)がゲームのテーマと一致しました。また、Phoenixの(短縮された)ニックネームが必要だったので(※訳注 日本語版でいえば「なるほどくん」にあたる愛称)、最終的にそれはNickになりました。 残念なことに、ここの誰もWendyOldbagの由来がわからないようです。最終的にはキャラクターの性格から由来されたものであり、今では他のネーミングは思いつきません。 NP What were some of the most radical changes made to any of thegame’scharacters or plot points? NP: ゲームのキャラクターやシナリオが根本的に変更された点は何かありますか? Brandon I am not sure any character underwent “radical” changes, as that wouldhavegreatly affected the overall arc of the game. Say changing a characterfrom“evil” to “good,” as this would have greatly altered the story fromtheoriginal concepts. The point that should be made is that while many aspectsofthe game had to be altered to suit the US player, we would be doing agreatdisservice to completely alter/change characters and/or plot points. Italsowould mean rewriting large parts of the game if we were to change keyplotpoints. We tried to walk the fine line of keeping the original visionwhilemaking an enjoyable game for English-speakers. Brandon: ゲーム全体に影響するので、「根本的な」変更はないと思っています。キャラが悪から善へと変わってしまえば、オリジナルのコンセプトから変えてしまうでしょう。アメリカのユーザーのために変えたら結局は大きな弊害になります。 JP There were concerns we would have to change some of the more mature sectionsofthe Japanese version, but luckily, everything was able to get throughunscathedeven though I had to tone down some things because concepts of age andmaturityare a bit different in the west. I think the biggest changes come tothe jokes.Some of them are just incomprehensible to westerners, and while thereis avocal set that wants everything exactly the same, I feel the jokes have tobemade culturally relevant to gamers. JP: 私たちは完成された日本版のうち、幾つか変更せねばならないかという懸念がありました。しかし、幸運にも、多少変えなくてはならない面がありましたが、全て根本的な変更はなく作成することができました。最大の変更点はジョーク関係でしょう。アメリカ人には理解できないジョークもありました。全て正確に海外のプレイヤーに伝えたいのであれば、ジョークも文化的に同じでないと無理だと思います。 Janet Plot-wise, we didn’t have to change anything, but character-wise, we hadafew things we had to change. For example, there is one character who is abiton the perverse side of things, and while it’s alright to make jokesaboutbeing perverse in Japanese culture, that sort of thing is not so welcomedinour own, so he had to be toned down. Janet: シナリオに関しては、変更する必要は全くありませんでした。しかし文字に関しては変更せざるを得ない部分がありました。例えば、日本文化では悪い性格の人物に対するジョークが問題ないのですが、それらの類は私たちにはあまり受け入れられないので、弱めた表現をせざるを得ませんでした。 NP What were some jokes that had to be completely reworked from theJapaneseversion? NP: 日本版から完全に変更しなければならなかったジョークは何ですか? Brandon A lot of the jokes that involve Phoenix’s last name “Wright” werenewjokes for the US version of the game. Since his name is not Phoenix Wrightinthe Japanese version, all of these jokes were new. Generally speaking, most of the jokes that appear in the English versionarequite different than the Japanese version due to the differences inhumor.Sarcasm, for instance, is not something that most Japanese people willfindhumorous. It was important to keep the overall humor of the game, but toconveyit in a way that an English-speaking audience could understand andfindfunny. Brandon: Phoenixの名字であるWrightは、英語版のために新しいジョークを作成するのに使われました。 一般的に、英語版でのジョークのほとんどは、日本語版とは全く異なります。皮肉は日本人にとってユーモラスだと感じないものもあります。しかし、英語圏のプレイヤーがユーモアを理解して、ゲームの総合的な面白さを保つのは重要でした。 JP My favorite example is when Moe goes crazy in case 3. Whenever caught in alie,he would launch into a stream of funny, but untranslatable gibberish. IntheEnglish version, Moe’s gibberish has become an upscale kind ofjibberjabber. JP: 私が好きな部分はMoe(トミー)が3話でクレイジーなトークをする場面です。愉快で翻訳できない、ワケのわからない話になってしまいます。英語版ではワケのわからない話は超早口のおしゃべりになっています。 Janet The humor of this game relies heavily on its jokes . . . we had to changequitea number of them. A lot of Japanese humor is derived from culturalreferences,but more than cultural references, this series is about wordplay.Takumi-san isa huge fan of playing with words to extract humor, and needless tosay,Japanese word-based jokes are not translatable. So we created a lot ofjokesfrom scratch. One of my personal favorites that we came up with has to dowithPearl and her comments about the TV remote in episode 4. Janet: このゲームの面白さはジョークにかかっています。私たちは、これらのほとんどを変えなくてはなりませんでした。日本の冗談には日本の文化が背景にあります。しかし、このシリーズでは文化的なものより、言葉のやりとりの面白さが目立っています。巧氏は言葉遊びの天才です、しかし、言うまでもなく、日本語に基づく冗談は翻訳できません。そこで、私たちはゼロから多くの冗談を作成しました。個人的に好きなもののひとつが、4話のPearl(春美)とのテレビに関するコメントです。 NP In the first Phoenix, the setting seemed to intentionally not be specified,butin Justice for All, there’s a distinctly Japanese village, and at thesametime, “the Heartland” is mentioned as “part of this country.”There’salso the matter of which side of the car the steering wheel is on. Howdid youdeal with these cultural and geographic issues? NP: 2作目では、明確に日本風の村と思われるものが登場し、同時に、故郷(=日本風の村)はこの国の一部(=アメリカの一部に日本っぽい村が出てきてしまったということ)となっています。また、車のハンドルがどちらについているかという問題もあります。これらの文化的、地理的問題をどう対処しましたか? Brandon The US version of Phoenix Wright Justice for All is set in the US. Wethinkthat while some aspects of the game may have a Japanese flair, itdoesn’tnecessarily mean that it is set in Japan. There are many areas withintheUnited States where Japanese culture and traditions are observed. Maya’shomevillage is one of these areas. Brandon: 北米版2はアメリカを舞台としています。ゲームの舞台には日本的なものがありますが、それらは日本でなくてはならないという意味ではないと考えています。アメリカにも日本文化と伝統が守られる地域があり、Maya(真宵)の故郷も、これらの地域のひとつだということです。 JP You change them to something culturally relevant to your targetaudience.Steering wheels, signboards, etc. all have to make sense to everyonepicking upand playing the game. While it has an anime feel, Phoenix Wrightshouldn’trequire a Japanese degree to play the English version. JP: 文化的に問題があるものを差し替えてみてください。ステアリングホイール、看板、その他は全て変更されています。英語版をプレイするときに、日本の知識は必要ありません。 Janet Actually, we set the English version of the game to take place in LosAngeles,hence the time-difference puzzle in the first game. However, had westated thatin the game, it probably would have ruined that puzzle. The culturalandgeographical issues were not as big of a problem as some people mightimagine.I personally feel that since the world of Phoenix Wright is clearly notourown, some differences can be allowed. Things like the steering wheelcancertainly be the same, but a Japanese-style village could theoreticallyexistif, say, the Fey family immigrated and then established their own villagein amountainous area of California. At least, that’s how I rationalizedit. ジャネット: 実際、1作目1話では時差のエピソードを差し替えていますが、それによって舞台がロサンゼルスになりました。しかし、文化的・地理的な問題は、さほど大きくはありませんでした。PhoenixWright世界では、それらのズレが許容されているのではないかと、個人的に思います。ハンドルのネタでも同じことがありますし、Fey(綾里)一族が移住してカリフォルニアの山岳地帯に村を作ったというような感じで合理的に説明ができるでしょう。 NP What characters did you especially enjoy writing for? Were there anycharactersthat were particularly challenging? NP: どのキャラクターのテキストを書くときに楽しかったですか? 特に思い出深いキャラはいますか? Brandon Some characters with extreme personality quirks are always both funandstressful to write for. Moe the clown, for example, presented a challengeofwriting for a clown who is no longer considered funny by anyone but himself.Itwas also important to show that this character had a big heart. So it wasachallenge to find the proper balance between silly jokes and seriousdialogueso that the player would not become annoyed by his “craziness.” Wethinkthe payoff, though, is well worth it when it is done right. We feel wewereable to create a character that the player will both like and dislike atthesame time. We believe this helps to create a more realistic andbelievablecharacter. Brandon: 極端な性格は常に面白く、また、書くことはストレスでもあります。例えば、Moe(トミー)はもう自分以外の誰によってもおかしすぎて考えられないピエロという挑戦でした。この人物が大物であることを示すのは重要でもありました。プレイヤーがストレスに悩まない程度にバカな冗談と重要な話との間でバランスをとることが要求されました。私たちは、プレイヤーに好まれたり、同時に嫌われたりするキャラを作ることができたと思います。このことで、リアルに存在するような人物を思い起こさせるでしょう。 JP Moe is my boy. I love him like a clown loves a Volkswagen. As far aschallengingcharacters, Acro sparked some heated arguments on how to get histone andpersonality right. JP: Moeはもはや自分の息子のようなものです。私はフォルクスワーゲンのマークのクラウン(英語ではピエロと王冠の意味の両方がある)並に彼が好きです。Acro(アクロ)はその個性について、熱い議論が交わされました。 Janet Wow, that’s tough. I enjoyed writing all of them, to be honest. Eachcharacterhad their own unique trait that I loved and even characters likeLotta Hart orWendy Oldbag, who some people found annoying, had their owncharm. But if I hadto pick three, I’d say Franziska von Karma, Shelly deKiller, and AdrianAndrews. As for challenging, I’d say Morgan Fey is thewinner. Her speechpattern in Japanese is a very old style and translating thatinto English was atough one. Janet: 私は全て楽しかったです。各々のキャラは彼ら独特のユニークな特徴を持ち、一部の人には腹立たしいと思われているらしい、LottaHart(大沢木ナツミ)やWendyOldbag(オバチャン)ですら魅力的でした。ベスト3はFranziskavonKarma(狩魔冥)とShelly deKiller(コロシヤ)、AdrianAndrews(華宮霧緒)です。難しかったのはMorganFey(綾里キミ子)で、彼女の日本語が古いスタイルだったので苦労しました。 NP Were there any big graphical changes that had to be made during thelocalizationprocess? NP: 翻訳のためにグラフィックを変えなくてはならない点はありましたか? Brandon As with most games that originate in Japan, there are graphics thathaveJapanese Kanji or other Japanese characters on them that have to be changedforan American version. Since Phoenix Wright doesn’t rely as heavily onchanginggraphics, the changes are not as difficult to make. Brandon: 日本からの大部分のゲームと同じく、日本語、漢字などのためにアメリカ版では変更しなくてはならないものがあります。大きな変更ではないので難しくはありません。 Janet There were a few changes that were made, and most had to do with changingsignsin the background and clues into their English counterparts. However, oneofthe more interesting changes had to do with how to change adistinctivelyJapanese seal into something more Western. We decided in the endthat if wewere to go with a signature, it would give the identity of the personaway, sowe dropped that part of the picture entirely. Janet: 幾つか変更点がありました。物語のヒントになる部分はグラフィック担当者にそれを伝えました。しかしながら、よりおもしろい変化のひとつはどのようにはっきりと日本語をより西洋の何かに変える方法を処理しなければなりませんでした。結局は認識のためにグラフィックを変えるのをやめました。 NP Did you have any localization troubles stemming from the differencesbetweenreal law and the way law is portrayed in the game? NP: 本当の法律との違いから翻訳に関するトラブルはありましたか? Brandon The world of Phoenix Wright is based more upon the Japanese structure oflawthan US law. While references and dialogue were able to be translatedintoEnglish, the law of the game still stayed fundamentally intact fromtheoriginal Japanese version. This is one area that we really couldn’tchangewithout altering the entire game structure. We could make referencesandcharacters relevant for US audiences, but to change the law structure ofthegame would have sacrificed what made the game so popular in the first place.Sofor American audiences, I am sure at times the laws of the Phoenix Wrightworldwill be quite wacky. Brandon: PhoenixWrightの世界は、アメリカの法律よりも日本の法律に基づいています。基本的に翻訳では日本版とはゲームのルールを変えることはしませんでした。アメリカの法律に基づくように変更もできましたが、ゲーム内での法律の構造を変えれば元のゲームが崩れてしまいます。ですので、アメリカ人には、PhoenixWrightの世界の法律は独自と言っています。 JP Nope. I don’t recommend playing Phoenix Wright to study for thebarexamination. JP: 司法試験のためにPhoenixWrightをプレイすることはお勧めできません。 Janet Actually, there is one that caused us to rethink how to phrase a fewsentencesin the game, but if I told you now, it would be a spoiler. Suffice tosay, theway the law is portrayed in the game is more Japanese than not, butenough ofit is different from real Japanese law that we could take similarlibertieswithin the confines of the American legal system. Janet: 実は、ゲーム中で2、3個ほどどう表すか再考したフレーズがあります。ここではネタバレになるので話しませんが。ゲーム内の法律は日本を元にしていますが、それらは私たちがアメリカの法律制度の範囲の中で類似した、自由に持っていくことができた本当の日本の法律と異なります。 NP What are your thoughts on Phoenix being successful enough to get a sequelinNorth America? NP: シリーズの続編を作るためには充分成功していると思われますが、いかがですか。 Brandon It is actually quite surprising that Phoenix Wright was successful in theUS.Text-based adventure games have been declining in popularity over the past10years or so. But it goes to show that people still love a good storycombinedwith a good mystery. We also think that people can really relate tothecharacters. In too many games there are very flat, one-dimensionalcharacters.In the world of Phoenix Wright, while the characters may appearwacky, theplayer can get a real sense of the makeup of each character. Webelieve thecharacters in Phoenix Wright are not so black-and-white, that theyfeel morelike real people. We believe this aspect is important in telling agood storyand people have picked up on that.Brandon: PhoenixWrightがアメリカで成功したことは、実際驚くべき出来事です。テキストアドベンチャーの人気はここ10年ほど落ち込んでいました。しかし、PhoenixWrightの成功は、良いミステリーとそれに基づくストーリーが好まれていることを示しています。これはキャラクター人気にも関連していると思います。多くのゲームでは平べったいキャラクターばかりですが、PhoenixWrightではキャラクターがリアルであると言えます。彼らがリアルな人物だと感じるために、白か黒かといった二次元論ではない部分があります。私たちはこれが良質のストーリーを生み出すのに重要であること、また、ゲーマーがそれに気づいたのだろうと思います。 JP Originally it wasn’t thought that the game could work in the States. It isatestament to both Takumi-san’s story and all of those involved inthelocalization that such a unique game could find a home where just a fewyearsago no one thought it was possible. JP: 当初、このゲームがアメリカで動くことになるとは思われませんでした。これは、数年前、誰も翻訳が可能だと思わなかった頃の巧氏の話と翻訳に関係するそのような面白いゲームを見つけることができたという証言です。 Janet All I can say is wow. I think Phoenix’s success has surprised everyonehere,but thank you, everyone, for your support. I hope Justice for All lives uptoits predecessor, and please look forward to more of the Ace Attorney seriesinthe future! Janet: とにかく大当たりだったと言えます。PhoenixWrightの成功に驚いたみなさんに、支援の謝意を表します。JusticeforAllの成功と、将来のAceAttorneyシリーズを楽しみにしていてください! ▲ページ上へ▲
https://w.atwiki.jp/earthquakeinfo_en/pages/43.html
Jo men Jens – det var jo det han begyndte at sove fra!Og sÃ¥ endte han med at fÃ¥ en lammer – ufint – men jeg ER utilregnelig om na#t;n t8230e. Og ja – du skal have en snak med dine naboer!! Henvis du bare til mig http //gmlasuy.com [url=http //hhlfxbrrd.com]hhlfxbrrd[/url] [link=http //nopqqperw.com]nopqqperw[/link]
https://w.atwiki.jp/feedback1970/pages/57.html
memo source 1 /* Licensed to the Apache Software Foundation (ASF) under one or more 2 * contributor license agreements. See the NOTICE file distributed with 3 * this work for additional information regarding copyright ownership. 4 * The ASF licenses this file to You under the Apache License, Version 2.0 5 * (the "License"); you may not use this file except in compliance with 6 * the License. You may obtain a copy of the License at 7 * 8 * http //www.apache.org/licenses/LICENSE-2.0 9 * 10 * Unless required by applicable law or agreed to in writing, software 11 * distributed under the License is distributed on an "AS IS" BASIS, 12 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 13 * See the License for the specific language governing permissions and 14 * limitations under the License. 15 */ 16 17 #ifndef APACHE_HTTP_CONFIG_H 18 #define APACHE_HTTP_CONFIG_H 19 20 #include "apr_hooks.h" 21 #include "util_cfgtree.h" 22 23 #ifdef __cplusplus 24 extern "C" { 25 #endif 26 27 /** 28 * @file http_config.h 29 * @brief Apache Configuration 30 */ 31 32 /* 33 * The central data structures around here... 34 */ 35 36 /* Command dispatch structures... */ 37 38 /** 39 * How the directives arguments should be parsed. 40 * @remark Note that for all of these except RAW_ARGS, the config routine is 41 * passed a freshly allocated string which can be modified or stored 42 * or whatever... 43 */ 44 enum cmd_how { 45 RAW_ARGS, /** cmd_func parses command line itself */ 46 TAKE1, /** one argument only */ 47 TAKE2, /** two arguments only */ 48 ITERATE, /** one argument, occuring multiple times 49 * (e.g., IndexIgnore) 50 */ 51 ITERATE2, /** two arguments, 2nd occurs multiple times 52 * (e.g., AddIcon) 53 */ 54 FLAG, /** One of On or Off */ 55 NO_ARGS, /** No args at all, e.g. /Directory */ 56 TAKE12, /** one or two arguments */ 57 TAKE3, /** three arguments only */ 58 TAKE23, /** two or three arguments */ 59 TAKE123, /** one, two or three arguments */ 60 TAKE13 /** one or three arguments */ 61 }; 62 /** 63 * This structure is passed to a command which is being invoked, 64 * to carry a large variety of miscellaneous data which is all of 65 * use to *somebody*... 66 */ 67 typedef struct cmd_parms_struct cmd_parms; 68 69 #if defined(AP_HAVE_DESIGNATED_INITIALIZER) || defined(DOXYGEN) 70 71 /** 72 * All the types of functions that can be used in directives 73 * @internal 74 */ 75 typedef union { 76 /** function to call for a no-args */ 77 const char *(*no_args) (cmd_parms *parms, void *mconfig); 78 /** function to call for a raw-args */ 79 const char *(*raw_args) (cmd_parms *parms, void *mconfig, 80 const char *args); 81 /** function to call for a take1 */ 82 const char *(*take1) (cmd_parms *parms, void *mconfig, const char *w); 83 /** function to call for a take2 */ 84 const char *(*take2) (cmd_parms *parms, void *mconfig, const char *w, 85 const char *w2); 86 /** function to call for a take3 */ 87 const char *(*take3) (cmd_parms *parms, void *mconfig, const char *w, 88 const char *w2, const char *w3); 89 /** function to call for a flag */ 90 const char *(*flag) (cmd_parms *parms, void *mconfig, int on); 91 } cmd_func; 92 93 /** This configuration directive does not take any arguments */ 94 # define AP_NO_ARGS func.no_args 95 /** This configuration directive will handle it s own parsing of arguments*/ 96 # define AP_RAW_ARGS func.raw_args 97 /** This configuration directive takes 1 argument*/ 98 # define AP_TAKE1 func.take1 99 /** This configuration directive takes 2 arguments */ 100 # define AP_TAKE2 func.take2 101 /** This configuration directive takes 3 arguments */ 102 # define AP_TAKE3 func.take3 103 /** This configuration directive takes a flag (on/off) as a argument*/ 104 # define AP_FLAG func.flag 105 106 /** method of declaring a directive with no arguments */ 107 # define AP_INIT_NO_ARGS(directive, func, mconfig, where, help) \ 108 { directive, { .no_args=func }, mconfig, where, RAW_ARGS, help } 109 /** method of declaring a directive with raw argument parsing */ 110 # define AP_INIT_RAW_ARGS(directive, func, mconfig, where, help) \ 111 { directive, { .raw_args=func }, mconfig, where, RAW_ARGS, help } 112 /** method of declaring a directive which takes 1 argument */ 113 # define AP_INIT_TAKE1(directive, func, mconfig, where, help) \ 114 { directive, { .take1=func }, mconfig, where, TAKE1, help } 115 /** method of declaring a directive which takes multiple arguments */ 116 # define AP_INIT_ITERATE(directive, func, mconfig, where, help) \ 117 { directive, { .take1=func }, mconfig, where, ITERATE, help } 118 /** method of declaring a directive which takes 2 arguments */ 119 # define AP_INIT_TAKE2(directive, func, mconfig, where, help) \ 120 { directive, { .take2=func }, mconfig, where, TAKE2, help } 121 /** method of declaring a directive which takes 1 or 2 arguments */ 122 # define AP_INIT_TAKE12(directive, func, mconfig, where, help) \ 123 { directive, { .take2=func }, mconfig, where, TAKE12, help } 124 /** method of declaring a directive which takes multiple 2 arguments */ 125 # define AP_INIT_ITERATE2(directive, func, mconfig, where, help) \ 126 { directive, { .take2=func }, mconfig, where, ITERATE2, help } 127 /** method of declaring a directive which takes 1 or 3 arguments */ 128 # define AP_INIT_TAKE13(directive, func, mconfig, where, help) \ 129 { directive, { .take3=func }, mconfig, where, TAKE13, help } 130 /** method of declaring a directive which takes 2 or 3 arguments */ 131 # define AP_INIT_TAKE23(directive, func, mconfig, where, help) \ 132 { directive, { .take3=func }, mconfig, where, TAKE23, help } 133 /** method of declaring a directive which takes 1 to 3 arguments */ 134 # define AP_INIT_TAKE123(directive, func, mconfig, where, help) \ 135 { directive, { .take3=func }, mconfig, where, TAKE123, help } 136 /** method of declaring a directive which takes 3 arguments */ 137 # define AP_INIT_TAKE3(directive, func, mconfig, where, help) \ 138 { directive, { .take3=func }, mconfig, where, TAKE3, help } 139 /** method of declaring a directive which takes a flag (on/off) as a argument*/ 140 # define AP_INIT_FLAG(directive, func, mconfig, where, help) \ 141 { directive, { .flag=func }, mconfig, where, FLAG, help } 142 143 #else /* AP_HAVE_DESIGNATED_INITIALIZER */ 144 145 typedef const char *(*cmd_func) (); 146 147 # define AP_NO_ARGS func 148 # define AP_RAW_ARGS func 149 # define AP_TAKE1 func 150 # define AP_TAKE2 func 151 # define AP_TAKE3 func 152 # define AP_FLAG func 153 154 # define AP_INIT_NO_ARGS(directive, func, mconfig, where, help) \ 155 { directive, func, mconfig, where, RAW_ARGS, help } 156 # define AP_INIT_RAW_ARGS(directive, func, mconfig, where, help) \ 157 { directive, func, mconfig, where, RAW_ARGS, help } 158 # define AP_INIT_TAKE1(directive, func, mconfig, where, help) \ 159 { directive, func, mconfig, where, TAKE1, help } 160 # define AP_INIT_ITERATE(directive, func, mconfig, where, help) \ 161 { directive, func, mconfig, where, ITERATE, help } 162 # define AP_INIT_TAKE2(directive, func, mconfig, where, help) \ 163 { directive, func, mconfig, where, TAKE2, help } 164 # define AP_INIT_TAKE12(directive, func, mconfig, where, help) \ 165 { directive, func, mconfig, where, TAKE12, help } 166 # define AP_INIT_ITERATE2(directive, func, mconfig, where, help) \ 167 { directive, func, mconfig, where, ITERATE2, help } 168 # define AP_INIT_TAKE13(directive, func, mconfig, where, help) \ 169 { directive, func, mconfig, where, TAKE13, help } 170 # define AP_INIT_TAKE23(directive, func, mconfig, where, help) \ 171 { directive, func, mconfig, where, TAKE23, help } 172 # define AP_INIT_TAKE123(directive, func, mconfig, where, help) \ 173 { directive, func, mconfig, where, TAKE123, help } 174 # define AP_INIT_TAKE3(directive, func, mconfig, where, help) \ 175 { directive, func, mconfig, where, TAKE3, help } 176 # define AP_INIT_FLAG(directive, func, mconfig, where, help) \ 177 { directive, func, mconfig, where, FLAG, help } 178 179 #endif /* AP_HAVE_DESIGNATED_INITIALIZER */ 180 181 /** 182 * The command record structure. Each modules can define a table of these 183 * to define the directives it will implement. 184 */ 185 typedef struct command_struct command_rec; 186 struct command_struct { 187 /** Name of this command */ 188 const char *name; 189 /** The function to be called when this directive is parsed */ 190 cmd_func func; 191 /** Extra data, for functions which implement multiple commands... */ 192 void *cmd_data; 193 /** What overrides need to be allowed to enable this command. */ 194 int req_override; 195 /** What the command expects as arguments 196 * @defvar cmd_how args_how*/ 197 enum cmd_how args_how; 198 199 /** usage message, in case of syntax errors */ 200 const char *errmsg; 201 }; 202 203 /** 204 * @defgroup ConfigDirectives Allowed locations for configuration directives. 205 * 206 * The allowed locations for a configuration directive are the union of 207 * those indicated by each set bit in the req_override mask. 208 * 209 * @{ 210 */ 211 #define OR_NONE 0 /** *.conf is not available anywhere in this override */ 212 #define OR_LIMIT 1 /** *.conf inside Directory or Location 213 and .htaccess when AllowOverride Limit */ 214 #define OR_OPTIONS 2 /** *.conf anywhere 215 and .htaccess when AllowOverride Options */ 216 #define OR_FILEINFO 4 /** *.conf anywhere 217 and .htaccess when AllowOverride FileInfo */ 218 #define OR_AUTHCFG 8 /** *.conf inside Directory or Location 219 and .htaccess when AllowOverride AuthConfig */ 220 #define OR_INDEXES 16 /** *.conf anywhere 221 and .htaccess when AllowOverride Indexes */ 222 #define OR_UNSET 32 /** unset a directive (in Allow) */ 223 #define ACCESS_CONF 64 /** *.conf inside Directory or Location */ 224 #define RSRC_CONF 128 /** *.conf outside Directory or Location */ 225 #define EXEC_ON_READ 256 /** force directive to execute a command 226 which would modify the configuration (like including another 227 file, or IFModule */ 228 /** this directive can be placed anywhere */ 229 #define OR_ALL (OR_LIMIT|OR_OPTIONS|OR_FILEINFO|OR_AUTHCFG|OR_INDEXES) 230 231 /** @} */ 232 233 /** 234 * This can be returned by a function if they don t wish to handle 235 * a command. Make it something not likely someone will actually use 236 * as an error code. 237 */ 238 #define DECLINE_CMD "\a\b" 239 240 /** Common structure for reading of config files / passwd files etc. */ 241 typedef struct ap_configfile_t ap_configfile_t; 242 struct ap_configfile_t { 243 int (*getch) (void *param); /** a getc()-like function */ 244 void *(*getstr) (void *buf, size_t bufsiz, void *param); 245 /** a fgets()-like function */ 246 int (*close) (void *param); /** a close handler function */ 247 void *param; /** the argument passed to getch/getstr/close */ 248 const char *name; /** the filename / description */ 249 unsigned line_number; /** current line number, starting at 1 */ 250 }; 251 252 /** 253 * This structure is passed to a command which is being invoked, 254 * to carry a large variety of miscellaneous data which is all of 255 * use to *somebody*... 256 */ 257 struct cmd_parms_struct { 258 /** Argument to command from cmd_table */ 259 void *info; 260 /** Which allow-override bits are set */ 261 int override; 262 /** Which methods are Limit ed */ 263 apr_int64_t limited; 264 /** methods which are limited */ 265 apr_array_header_t *limited_xmethods; 266 /** methods which are xlimited */ 267 ap_method_list_t *xlimited; 268 269 /** Config file structure. */ 270 ap_configfile_t *config_file; 271 /** the directive specifying this command */ 272 ap_directive_t *directive; 273 274 /** Pool to allocate new storage in */ 275 apr_pool_t *pool; 276 /** Pool for scratch memory; persists during configuration, but 277 * wiped before the first request is served... */ 278 apr_pool_t *temp_pool; 279 /** Server_rec being configured for */ 280 server_rec *server; 281 /** If configuring for a directory, pathname of that directory. 282 * NOPE! That s what it meant previous to the existance of Files , 283 * Location and regex matching. Now the only usefulness that can be 284 * derived from this field is whether a command is being called in a 285 * server context (path == NULL) or being called in a dir context 286 * (path != NULL). */ 287 char *path; 288 /** configuration command */ 289 const command_rec *cmd; 290 291 /** per_dir_config vector passed to handle_command */ 292 struct ap_conf_vector_t *context; 293 /** directive with syntax error */ 294 const ap_directive_t *err_directive; 295 }; 296 297 /** 298 * Module structures. Just about everything is dispatched through 299 * these, directly or indirectly (through the command and handler 300 * tables). 301 */ 302 typedef struct module_struct module; 303 struct module_struct { 304 /** API version, *not* module version; check that module is 305 * compatible with this version of the server. 306 */ 307 int version; 308 /** API minor version. Provides API feature milestones. Not checked 309 * during module init */ 310 int minor_version; 311 /** Index to this modules structures in config vectors. */ 312 int module_index; 313 314 /** The name of the module s C file */ 315 const char *name; 316 /** The handle for the DSO. Internal use only */ 317 void *dynamic_load_handle; 318 319 /** A pointer to the next module in the list 320 * @defvar module_struct *next */ 321 struct module_struct *next; 322 323 /** Magic Cookie to identify a module structure; It s mainly 324 * important for the DSO facility (see also mod_so). */ 325 unsigned long magic; 326 327 /** Function to allow MPMs to re-write command line arguments. This 328 * hook is only available to MPMs. 329 * @param The process that the server is running in. 330 */ 331 void (*rewrite_args) (process_rec *process); 332 /** Function to allow all modules to create per directory configuration 333 * structures. 334 * @param p The pool to use for all allocations. 335 * @param dir The directory currently being processed. 336 * @return The per-directory structure created 337 */ 338 void *(*create_dir_config) (apr_pool_t *p, char *dir); 339 /** Function to allow all modules to merge the per directory configuration 340 * structures for two directories. 341 * @param p The pool to use for all allocations. 342 * @param base_conf The directory structure created for the parent directory. 343 * @param new_conf The directory structure currently being processed. 344 * @return The new per-directory structure created 345 */ 346 void *(*merge_dir_config) (apr_pool_t *p, void *base_conf, void *new_conf); 347 /** Function to allow all modules to create per server configuration 348 * structures. 349 * @param p The pool to use for all allocations. 350 * @param s The server currently being processed. 351 * @return The per-server structure created 352 */ 353 void *(*create_server_config) (apr_pool_t *p, server_rec *s); 354 /** Function to allow all modules to merge the per server configuration 355 * structures for two servers. 356 * @param p The pool to use for all allocations. 357 * @param base_conf The directory structure created for the parent directory. 358 * @param new_conf The directory structure currently being processed. 359 * @return The new per-directory structure created 360 */ 361 void *(*merge_server_config) (apr_pool_t *p, void *base_conf, 362 void *new_conf); 363 364 /** A command_rec table that describes all of the directives this module 365 * defines. */ 366 const command_rec *cmds; 367 368 /** A hook to allow modules to hook other points in the request processing. 369 * In this function, modules should call the ap_hook_*() functions to 370 * register an interest in a specific step in processing the current 371 * request. 372 * @param p the pool to use for all allocations 373 */ 374 void (*register_hooks) (apr_pool_t *p); 375 }; 376 377 /** 378 * @defgroup ModuleInit Module structure initializers 379 * 380 * Initializer for the first few module slots, which are only 381 * really set up once we start running. Note that the first two slots 382 * provide a version check; this should allow us to deal with changes to 383 * the API. The major number should reflect changes to the API handler table 384 * itself or removal of functionality. The minor number should reflect 385 * additions of functionality to the existing API. (the server can detect 386 * an old-format module, and either handle it back-compatibly, or at least 387 * signal an error). See src/include/ap_mmn.h for MMN version history. 388 * @{ 389 */ 390 391 /** The one used in Apache 1.3, which will deliberately cause an error */ 392 #define STANDARD_MODULE_STUFF this_module_needs_to_be_ported_to_apache_2_0 393 394 /** Use this in all standard modules */ 395 #define STANDARD20_MODULE_STUFF MODULE_MAGIC_NUMBER_MAJOR, \ 396 MODULE_MAGIC_NUMBER_MINOR, \ 397 -1, \ 398 __FILE__, \ 399 NULL, \ 400 NULL, \ 401 MODULE_MAGIC_COOKIE, \ 402 NULL /* rewrite args spot */ 403 404 /** Use this only in MPMs */ 405 #define MPM20_MODULE_STUFF MODULE_MAGIC_NUMBER_MAJOR, \ 406 MODULE_MAGIC_NUMBER_MINOR, \ 407 -1, \ 408 __FILE__, \ 409 NULL, \ 410 NULL, \ 411 MODULE_MAGIC_COOKIE 412 413 /** @} */ 414 415 /* CONFIGURATION VECTOR FUNCTIONS */ 416 417 /** configuration vector structure */ 418 typedef struct ap_conf_vector_t ap_conf_vector_t; 419 420 /** 421 * Generic accessors for other modules to get at their own module-specific 422 * data 423 * @param conf_vector The vector in which the modules configuration is stored. 424 * usually r- per_dir_config or s- module_config 425 * @param m The module to get the data for. 426 * @return The module-specific data 427 */ 428 AP_DECLARE(void *) ap_get_module_config(const ap_conf_vector_t *cv, 429 const module *m); 430 431 /** 432 * Generic accessors for other modules to set at their own module-specific 433 * data 434 * @param conf_vector The vector in which the modules configuration is stored. 435 * usually r- per_dir_config or s- module_config 436 * @param m The module to set the data for. 437 * @param val The module-specific data to set 438 */ 439 AP_DECLARE(void) ap_set_module_config(ap_conf_vector_t *cv, const module *m, 440 void *val); 441 442 #if !defined(AP_DEBUG) 443 444 #define ap_get_module_config(v,m) \ 445 (((void **)(v))[(m)- module_index]) 446 #define ap_set_module_config(v,m,val) \ 447 ((((void **)(v))[(m)- module_index]) = (val)) 448 449 #endif /* AP_DEBUG */ 450 451 452 /** 453 * Generic command handling function for strings 454 * @param cmd The command parameters for this directive 455 * @param struct_ptr pointer into a given type 456 * @param arg The argument to the directive 457 * @return An error string or NULL on success 458 */ 459 AP_DECLARE_NONSTD(const char *) ap_set_string_slot(cmd_parms *cmd, 460 void *struct_ptr, 461 const char *arg); 462 463 /** 464 * Generic command handling function for integers 465 * @param cmd The command parameters for this directive 466 * @param struct_ptr pointer into a given type 467 * @param arg The argument to the directive 468 * @return An error string or NULL on success 469 */ 470 AP_DECLARE_NONSTD(const char *) ap_set_int_slot(cmd_parms *cmd, 471 void *struct_ptr, 472 const char *arg); 473 474 /** 475 * Return true if the specified method is limited by being listed in 476 * a Limit container, or by *not* being listed in a LimiteExcept 477 * container. 478 * 479 * @param method Pointer to a string specifying the method to check. 480 * @param cmd Pointer to the cmd_parms structure passed to the 481 * directive handler. 482 * @return 0 if the method is not limited in the current scope 483 */ 484 AP_DECLARE(int) ap_method_is_limited(cmd_parms *cmd, const char *method); 485 486 /** 487 * Generic command handling function for strings, always sets the value 488 * to a lowercase string 489 * @param cmd The command parameters for this directive 490 * @param struct_ptr pointer into a given type 491 * @param arg The argument to the directive 492 * @return An error string or NULL on success 493 */ 494 AP_DECLARE_NONSTD(const char *) ap_set_string_slot_lower(cmd_parms *cmd, 495 void *struct_ptr, 496 const char *arg); 497 /** 498 * Generic command handling function for flags 499 * @param cmd The command parameters for this directive 500 * @param struct_ptr pointer into a given type 501 * @param arg The argument to the directive (either 1 or 0) 502 * @return An error string or NULL on success 503 */ 504 AP_DECLARE_NONSTD(const char *) ap_set_flag_slot(cmd_parms *cmd, 505 void *struct_ptr, 506 int arg); 507 /** 508 * Generic command handling function for files 509 * @param cmd The command parameters for this directive 510 * @param struct_ptr pointer into a given type 511 * @param arg The argument to the directive 512 * @return An error string or NULL on success 513 */ 514 AP_DECLARE_NONSTD(const char *) ap_set_file_slot(cmd_parms *cmd, 515 void *struct_ptr, 516 const char *arg); 517 /** 518 * Generic command handling function to respond with cmd- help as an error 519 * @param cmd The command parameters for this directive 520 * @param struct_ptr pointer into a given type 521 * @param arg The argument to the directive 522 * @return The cmd- help value as the error string 523 * @tip This allows simple declarations such as; 524 * pre 525 * AP_INIT_RAW_ARGS("Foo", ap_set_deprecated, NULL, OR_ALL, 526 * "The Foo directive is no longer supported, use Bar"), 527 * /pre 528 */ 529 AP_DECLARE_NONSTD(const char *) ap_set_deprecated(cmd_parms *cmd, 530 void *struct_ptr, 531 const char *arg); 532 /** 533 * For modules which need to read config files, open logs, etc. this returns 534 * the canonical form of fname made absolute to ap_server_root. 535 * @param p pool to allocate data from 536 * @param fname The file name 537 */ 538 AP_DECLARE(char *) ap_server_root_relative(apr_pool_t *p, const char *fname); 539 540 /* Finally, the hook for dynamically loading modules in... */ 541 542 /** 543 * Add a module to the server 544 * @param m The module structure of the module to add 545 * @param p The pool of the same lifetime as the module 546 */ 547 AP_DECLARE(void) ap_add_module(module *m, apr_pool_t *p); 548 549 /** 550 * Remove a module from the server. There are some caveats 551 * when the module is removed, its slot is lost so all the current 552 * per-dir and per-server configurations are invalid. So we should 553 * only ever call this function when you are invalidating almost 554 * all our current data. I.e. when doing a restart. 555 * @param m the module structure of the module to remove 556 */ 557 AP_DECLARE(void) ap_remove_module(module *m); 558 /** 559 * Add a module to the chained modules list and the list of loaded modules 560 * @param m The module structure of the module to add 561 * @param p The pool with the same lifetime as the module 562 */ 563 AP_DECLARE(void) ap_add_loaded_module(module *mod, apr_pool_t *p); 564 /** 565 * Remove a module fromthe chained modules list and the list of loaded modules 566 * @param m the module structure of the module to remove 567 */ 568 AP_DECLARE(void) ap_remove_loaded_module(module *mod); 569 /** 570 * Add a module to the list of loaded module based on the name of the 571 * module 572 * @param name The name of the module 573 * @param p The pool valid for the lifetime of the module 574 * @return 1 on success, 0 on failure 575 */ 576 AP_DECLARE(int) ap_add_named_module(const char *name, apr_pool_t *p); 577 /** 578 * Find the name of the specified module 579 * @param m The module to get the name for 580 * @return the name of the module 581 */ 582 AP_DECLARE(const char *) ap_find_module_name(module *m); 583 /** 584 * Find a module based on the name of the module 585 * @param name the name of the module 586 * @return the module structure if found, NULL otherwise 587 */ 588 AP_DECLARE(module *) ap_find_linked_module(const char *name); 589 590 /** 591 * Open a ap_configfile_t as apr_file_t 592 * @param ret_cfg open ap_configfile_t struct pointer 593 * @param p The pool to allocate the structure from 594 * @param name the name of the file to open 595 */ 596 AP_DECLARE(apr_status_t) ap_pcfg_openfile(ap_configfile_t **ret_cfg, 597 apr_pool_t *p, const char *name); 598 599 /** 600 * Allocate a ap_configfile_t handle with user defined functions and params 601 * @param p The pool to allocate from 602 * @param descr The name of the file 603 * @param param The argument passed to getch/getstr/close 604 * @param getc_func The getch function 605 * @param gets_func The getstr function 606 * @param close_func The close function 607 */ 608 AP_DECLARE(ap_configfile_t *) ap_pcfg_open_custom(apr_pool_t *p, 609 const char *descr, 610 void *param, 611 int(*getc_func)(void*), 612 void *(*gets_func) (void *buf, size_t bufsiz, void *param), 613 int(*close_func)(void *param)); 614 615 /** 616 * Read one line from open ap_configfile_t, strip LF, increase line number 617 * @param buf place to store the line read 618 * @param bufsize size of the buffer 619 * @param cfp File to read from 620 * @return 1 on success, 0 on failure 621 */ 622 AP_DECLARE(int) ap_cfg_getline(char *buf, size_t bufsize, ap_configfile_t *cfp); 623 624 /** 625 * Read one char from open configfile_t, increase line number upon LF 626 * @param cfp The file to read from 627 * @return the character read 628 */ 629 AP_DECLARE(int) ap_cfg_getc(ap_configfile_t *cfp); 630 631 /** 632 * Detach from open ap_configfile_t, calling the close handler 633 * @param cfp The file to close 634 * @return 1 on sucess, 0 on failure 635 */ 636 AP_DECLARE(int) ap_cfg_closefile(ap_configfile_t *cfp); 637 638 /** 639 * Read all data between the current foo and the matching /foo . All 640 * of this data is forgotten immediately. 641 * @param cmd The cmd_parms to pass to the directives inside the container 642 * @param directive The directive name to read until 643 * @return Error string on failure, NULL on success 644 */ 645 AP_DECLARE(const char *) ap_soak_end_container(cmd_parms *cmd, char *directive); 646 647 /** 648 * Read all data between the current foo and the matching /foo and build 649 * a config tree from it 650 * @param p pool to allocate from 651 * @param temp_pool Temporary pool to allocate from 652 * @param parms The cmd_parms to pass to all directives read 653 * @param current The current node in the tree 654 * @param curr_parent The current parent node 655 * @param orig_directive The directive to read until hit. 656 * @return Error string on failure, NULL on success 657 */ 658 AP_DECLARE(const char *) ap_build_cont_config(apr_pool_t *p, 659 apr_pool_t *temp_pool, 660 cmd_parms *parms, 661 ap_directive_t **current, 662 ap_directive_t **curr_parent, 663 char *orig_directive); 664 665 /** 666 * Build a config tree from a config file 667 * @param parms The cmd_parms to pass to all of the directives in the file 668 * @param conf_pool The pconf pool 669 * @param temp_pool The temporary pool 670 * @param conftree Place to store the root node of the config tree 671 * @return Error string on erro, NULL otherwise 672 */ 673 AP_DECLARE(const char *) ap_build_config(cmd_parms *parms, 674 apr_pool_t *conf_pool, 675 apr_pool_t *temp_pool, 676 ap_directive_t **conftree); 677 678 /** 679 * Walk a config tree and setup the server s internal structures 680 * @param conftree The config tree to walk 681 * @param parms The cmd_parms to pass to all functions 682 * @param section_vector The per-section config vector. 683 * @return Error string on error, NULL otherwise 684 */ 685 AP_DECLARE(const char *) ap_walk_config(ap_directive_t *conftree, 686 cmd_parms *parms, 687 ap_conf_vector_t *section_vector); 688 689 /** 690 * @defgroup ap_check_cmd_context ap_check_cmd_context 691 * @{ 692 */ 693 /** 694 * Check the context a command is used in. 695 * @param cmd The command to check 696 * @param forbidden Where the command is forbidden. 697 * @return Error string on error, NULL on success 698 */ 699 AP_DECLARE(const char *) ap_check_cmd_context(cmd_parms *cmd, 700 unsigned forbidden); 701 702 #define NOT_IN_VIRTUALHOST 0x01 /** Forbidden in Virtualhost */ 703 #define NOT_IN_LIMIT 0x02 /** Forbidden in Limit */ 704 #define NOT_IN_DIRECTORY 0x04 /** Forbidden in Directory */ 705 #define NOT_IN_LOCATION 0x08 /** Forbidden in Location */ 706 #define NOT_IN_FILES 0x10 /** Forbidden in Files */ 707 /** Forbidden in Directory / Location / Files */ 708 #define NOT_IN_DIR_LOC_FILE (NOT_IN_DIRECTORY|NOT_IN_LOCATION|NOT_IN_FILES) 709 /** Forbidden in VirtualHost / Limit / Directory / Location / Files */ 710 #define GLOBAL_ONLY (NOT_IN_VIRTUALHOST|NOT_IN_LIMIT|NOT_IN_DIR_LOC_FILE) 711 712 /** @} */ 713 714 #ifdef CORE_PRIVATE 715 716 /** 717 * The topmost module in the list 718 * @defvar module *ap_top_module 719 */ 720 AP_DECLARE_DATA extern module *ap_top_module; 721 722 /** 723 * Array of all statically linked modules 724 * @defvar module *ap_prelinked_modules[] 725 */ 726 AP_DECLARE_DATA extern module *ap_prelinked_modules[]; 727 /** 728 * Array of all preloaded modules 729 * @defvar module *ap_preloaded_modules[] 730 */ 731 AP_DECLARE_DATA extern module *ap_preloaded_modules[]; 732 /** 733 * Array of all loaded modules 734 * @defvar module **ap_loaded_modules 735 */ 736 AP_DECLARE_DATA extern module **ap_loaded_modules; 737 738 /* For mod_so.c... */ 739 /** Run a single module s two create_config hooks 740 * @param p the pool to allocate from 741 * @param s The server to configure for. 742 * @param m The module to configure 743 */ 744 AP_DECLARE(void) ap_single_module_configure(apr_pool_t *p, server_rec *s, 745 module *m); 746 747 /* For http_main.c... */ 748 /** 749 * Add all of the prelinked modules into the loaded module list 750 * @param process The process that is currently running the server 751 */ 752 AP_DECLARE(void) ap_setup_prelinked_modules(process_rec *process); 753 754 /** 755 * Show the preloaded configuration directives, the help string explaining 756 * the directive arguments, in what module they are handled, and in 757 * what parts of the configuration they are allowed. Used for httpd -h. 758 */ 759 AP_DECLARE(void) ap_show_directives(void); 760 761 /** 762 * Show the preloaded module names. Used for httpd -l. 763 */ 764 AP_DECLARE(void) ap_show_modules(void); 765 766 /** 767 * Show the MPM name. Used in reporting modules such as mod_info to 768 * provide extra information to the user 769 */ 770 AP_DECLARE(const char *) ap_show_mpm(void); 771 772 /** 773 * Read all config files and setup the server 774 * @param process The process running the server 775 * @param temp_pool A pool to allocate temporary data from. 776 * @param config_name The name of the config file 777 * @param conftree Place to store the root of the config tree 778 * @return The setup server_rec list. 779 */ 780 AP_DECLARE(server_rec *) ap_read_config(process_rec *process, 781 apr_pool_t *temp_pool, 782 const char *config_name, 783 ap_directive_t **conftree); 784 785 /** 786 * Run all rewrite args hooks for loaded modules 787 * @param process The process currently running the server 788 */ 789 AP_DECLARE(void) ap_run_rewrite_args(process_rec *process); 790 791 /** 792 * Run the register hooks function for a specified module 793 * @param m The module to run the register hooks function fo 794 * @param p The pool valid for the lifetime of the module 795 */ 796 AP_DECLARE(void) ap_register_hooks(module *m, apr_pool_t *p); 797 798 /** 799 * Setup all virtual hosts 800 * @param p The pool to allocate from 801 * @param main_server The head of the server_rec list 802 */ 803 AP_DECLARE(void) ap_fixup_virtual_hosts(apr_pool_t *p, 804 server_rec *main_server); 805 806 /* For http_request.c... */ 807 808 /** 809 * Setup the config vector for a request_rec 810 * @param p The pool to allocate the config vector from 811 * @return The config vector 812 */ 813 AP_CORE_DECLARE(ap_conf_vector_t*) ap_create_request_config(apr_pool_t *p); 814 815 /** 816 * Setup the config vector for per dir module configs 817 * @param p The pool to allocate the config vector from 818 * @return The config vector 819 */ 820 AP_CORE_DECLARE(ap_conf_vector_t *) ap_create_per_dir_config(apr_pool_t *p); 821 822 /** 823 * Run all of the modules merge per dir config functions 824 * @param p The pool to pass to the merge functions 825 * @param base The base directory config structure 826 * @param new_conf The new directory config structure 827 */ 828 AP_CORE_DECLARE(ap_conf_vector_t*) ap_merge_per_dir_configs(apr_pool_t *p, 829 ap_conf_vector_t *base, 830 ap_conf_vector_t *new_conf); 831 832 /* For http_connection.c... */ 833 /** 834 * Setup the config vector for a connection_rec 835 * @param p The pool to allocate the config vector from 836 * @return The config vector 837 */ 838 AP_CORE_DECLARE(ap_conf_vector_t*) ap_create_conn_config(apr_pool_t *p); 839 840 /* For http_core.c... ( Directory command and virtual hosts) */ 841 842 /** 843 * parse an htaccess file 844 * @param resulting htaccess_result 845 * @param r The request currently being served 846 * @param override Which overrides are active 847 * @param path The path to the htaccess file 848 * @param access_name The list of possible names for .htaccess files 849 * int The status of the current request 850 */ 851 AP_CORE_DECLARE(int) ap_parse_htaccess(ap_conf_vector_t **result, 852 request_rec *r, int override, 853 const char *path, 854 const char *access_name); 855 856 /** 857 * Setup a virtual host 858 * @param p The pool to allocate all memory from 859 * @param hostname The hostname of the virtual hsot 860 * @param main_server The main server for this Apache configuration 861 * @param ps Place to store the new server_rec 862 * return Error string on error, NULL on success 863 */ 864 AP_CORE_DECLARE(const char *) ap_init_virtual_host(apr_pool_t *p, 865 const char *hostname, 866 server_rec *main_server, 867 server_rec **); 868 869 /** 870 * Process the config file for Apache 871 * @param s The server rec to use for the command parms 872 * @param fname The name of the config file 873 * @param conftree The root node of the created config tree 874 * @param p Pool for general allocation 875 * @param ptem Pool for temporary allocation 876 */ 877 AP_DECLARE(void) ap_process_resource_config(server_rec *s, const char *fname, 878 ap_directive_t **conftree, 879 apr_pool_t *p, apr_pool_t *ptemp); 880 881 /** 882 * Process all directives in the config tree 883 * @param s The server rec to use in the command parms 884 * @param conftree The config tree to process 885 * @param p The pool for general allocation 886 * @param ptemp The pool for temporary allocations 887 */ 888 AP_DECLARE(void) ap_process_config_tree(server_rec *s, ap_directive_t *conftree, 889 apr_pool_t *p, apr_pool_t *ptemp); 890 891 /* Module-method dispatchers, also for http_request.c */ 892 /** 893 * Run the handler phase of each module until a module accepts the 894 * responsibility of serving the request 895 * @param r The current request 896 * @return The status of the current request 897 */ 898 AP_CORE_DECLARE(int) ap_invoke_handler(request_rec *r); 899 900 /* for mod_perl */ 901 902 /** 903 * Find a given directive in a command_rec table 904 * @param name The directive to search for 905 * @param cmds The table to search 906 * @return The directive definition of the specified directive 907 */ 908 AP_CORE_DECLARE(const command_rec *) ap_find_command(const char *name, 909 const command_rec *cmds); 910 911 /** 912 * Find a given directive in a list module 913 * @param cmd_name The directive to search for 914 * @param mod The module list to search 915 * @return The directive definition of the specified directive 916 */ 917 AP_CORE_DECLARE(const command_rec *) ap_find_command_in_modules(const char *cmd_name, 918 module **mod); 919 920 /** 921 * Ask a module to create per-server and per-section (dir/loc/file) configs 922 * (if it hasn t happened already). The results are stored in the server s 923 * config, and the specified per-section config vector. 924 * @param server The server to operate upon. 925 * @param section_vector The per-section config vector. 926 * @param section Which section to create a config for. 927 * @param mod The module which is defining the config data. 928 * @param pconf A pool for all configuration allocations. 929 * @return The (new) per-section config data. 930 */ 931 AP_CORE_DECLARE(void *) ap_set_config_vectors(server_rec *server, 932 ap_conf_vector_t *section_vector, 933 const char *section, 934 module *mod, apr_pool_t *pconf); 935 936 #endif 937 938 /* Hooks */ 939 940 /** 941 * Run the header parser functions for each module 942 * @param r The current request 943 * @return OK or DECLINED 944 */ 945 AP_DECLARE_HOOK(int,header_parser,(request_rec *r)) 946 947 /** 948 * Run the pre_config function for each module 949 * @param pconf The config pool 950 * @param plog The logging streams pool 951 * @param ptemp The temporary pool 952 * @return OK or DECLINED on success anything else is a error 953 */ 954 AP_DECLARE_HOOK(int,pre_config,(apr_pool_t *pconf,apr_pool_t *plog, 955 apr_pool_t *ptemp)) 956 957 958 /** 959 * Run the post_config function for each module 960 * @param pconf The config pool 961 * @param plog The logging streams pool 962 * @param ptemp The temporary pool 963 * @param s The list of server_recs 964 * @return OK or DECLINED on success anything else is a error 965 */ 966 AP_DECLARE_HOOK(int,post_config,(apr_pool_t *pconf,apr_pool_t *plog, 967 apr_pool_t *ptemp,server_rec *s)) 968 969 /** 970 * Run the open_logs functions for each module 971 * @param pconf The config pool 972 * @param plog The logging streams pool 973 * @param ptemp The temporary pool 974 * @param s The list of server_recs 975 * @return OK or DECLINED on success anything else is a error 976 */ 977 AP_DECLARE_HOOK(int,open_logs,(apr_pool_t *pconf,apr_pool_t *plog, 978 apr_pool_t *ptemp,server_rec *s)) 979 980 /** 981 * Run the child_init functions for each module 982 * @param pchild The child pool 983 * @param s The list of server_recs in this server 984 */ 985 AP_DECLARE_HOOK(void,child_init,(apr_pool_t *pchild, server_rec *s)) 986 987 /** 988 * Run the handler functions for each module 989 * @param r The request_rec 990 * @remark non-wildcard handlers should HOOK_MIDDLE, wildcard HOOK_LAST 991 */ 992 AP_DECLARE_HOOK(int,handler,(request_rec *r)) 993 994 /** 995 * Run the quick handler functions for each module. The quick_handler 996 * is run before any other requests hooks are called (location_walk, 997 * directory_walk, access checking, et. al.). This hook was added 998 * to provide a quick way to serve content from a URI keyed cache. 999 * 1000 * @param r The request_rec 1001 * @param lookup_uri Controls whether the caller actually wants content or not. 1002 * lookup is set when the quick_handler is called out of 1003 * ap_sub_req_lookup_uri() 1004 */ 1005 AP_DECLARE_HOOK(int,quick_handler,(request_rec *r, int lookup_uri)) 1006 1007 /** 1008 * Retrieve the optional functions for each module. 1009 * This is run immediately before the server starts. Optional functions should 1010 * be registered during the hook registration phase. 1011 */ 1012 AP_DECLARE_HOOK(void,optional_fn_retrieve,(void)) 1013 1014 #ifdef __cplusplus 1015 } 1016 #endif 1017 1018 #endif /* !APACHE_HTTP_CONFIG_H */
https://w.atwiki.jp/tanem/pages/22.html
Tips 設定ファイルを「Application Data」配下でなく任意のフォルダに保存する方法: Sylpheedインストールディレクトリ(%Sylepheed_Home%)直下の「sample-sylpheed.ini」をコピーして「sylpheed.ini」を作成する。 必要に応じて「sylpheed.ini」のconfigdirの値を編集することで、任意のディレクトリ配下に設定ファイルを保存することができる。 (デフォルトでは%Sylepheed_Home%\configディレクトリ配下に設定ファイルが保存される) (参考)「sylpheed.ini」の内容 [Sylpheed] ipcport=50215 configdir=config 各種設定ファイル 設定ファイル名 保存される情報 accountrc アカウントの設定。 folderlist.xml フォルダの情報。 filter.xml 振り分けの設定。 移行時の対象物 sylpheed.ini 設定ファイルのフォルダ (例)%Sylepheed_Home%\config メールデータのフォルダ (例)%Sylepheed_Home%\config\MailBoxes